Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: eb681c48cecc80cba153b973df6990836ad90f1ff78f3633c324fa866f965728

Tx prefix hash: 861c9bf3f970e670e893b83c78a93a8eee29106ec74e4a95e9afe5ad3afdc048
Tx public key: d86e99c68c5d639277d604e0694b701e72062ec2ab9a0fa9e6dfe6a26b5306c0
Timestamp: 1707500990 Timestamp [UCT]: 2024-02-09 17:49:50 Age [y:d:h:m:s]: 00:350:00:25:43
Block: 953923 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250525 RingCT/type: yes/0
Extra: 01d86e99c68c5d639277d604e0694b701e72062ec2ab9a0fa9e6dfe6a26b5306c00211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26d706e5b5b25a60ecbe11d9ecd790d551fcf13665807ab1eeaa40335339f455 0.600000000000 1413195 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 953933, "vin": [ { "gen": { "height": 953923 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26d706e5b5b25a60ecbe11d9ecd790d551fcf13665807ab1eeaa40335339f455" } } ], "extra": [ 1, 216, 110, 153, 198, 140, 93, 99, 146, 119, 214, 4, 224, 105, 75, 112, 30, 114, 6, 46, 194, 171, 154, 15, 169, 230, 223, 230, 162, 107, 83, 6, 192, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8