Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfb580ffa895095332cfb67312b1f499db31fc716c9a26fd1a0f1973749cdb73

Tx prefix hash: c2ad99180c58ab4b97dd07f925eaa368ae54a70b09a587662733d5b6faa60928
Tx public key: 6e9b2262ee3dc6a7203f699c4f9d428b0105b0427a763c9a546b2800aac73c8b
Timestamp: 1718092217 Timestamp [UCT]: 2024-06-11 07:50:17 Age [y:d:h:m:s]: 00:174:12:55:40
Block: 1041749 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124927 RingCT/type: yes/0
Extra: 016e9b2262ee3dc6a7203f699c4f9d428b0105b0427a763c9a546b2800aac73c8b0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b75a3963224cdb7ebe7e56fcbbb79862fae9dbe14500654611f944a26ce3ea4a 0.600000000000 1510498 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": 1041759, "vin": [ { "gen": { "height": 1041749 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b75a3963224cdb7ebe7e56fcbbb79862fae9dbe14500654611f944a26ce3ea4a" } } ], "extra": [ 1, 110, 155, 34, 98, 238, 61, 198, 167, 32, 63, 105, 156, 79, 157, 66, 139, 1, 5, 176, 66, 122, 118, 60, 154, 84, 107, 40, 0, 170, 199, 60, 139, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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