Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 973db9b0fe90f7c3938bcc808eb49f73e15c255006f0647a28381947b0749a73

Tx prefix hash: 8a4f25fb629ac86fcfc0132492900b08f231906283b5895879ff880ff0006e41
Tx public key: 7de3b6b5a42f48d33b902e2ee8691fea63c6e4258b40afe506560d8e01ed8b46
Timestamp: 1714665827 Timestamp [UCT]: 2024-05-02 16:03:47 Age [y:d:h:m:s]: 00:196:07:48:34
Block: 1013334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140538 RingCT/type: yes/0
Extra: 017de3b6b5a42f48d33b902e2ee8691fea63c6e4258b40afe506560d8e01ed8b460211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c806f1aba1dd44e491029e6fd3ef2c646e84aa35a9784d0d2acd6de1470aec71 0.600000000000 1476125 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": 1013344, "vin": [ { "gen": { "height": 1013334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c806f1aba1dd44e491029e6fd3ef2c646e84aa35a9784d0d2acd6de1470aec71" } } ], "extra": [ 1, 125, 227, 182, 181, 164, 47, 72, 211, 59, 144, 46, 46, 232, 105, 31, 234, 99, 198, 228, 37, 139, 64, 175, 229, 6, 86, 13, 142, 1, 237, 139, 70, 2, 17, 0, 0, 0, 1, 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