Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a44200686321b12d43d782af12d8877deae80939e4a20080116a22782ce708e8

Tx prefix hash: 70a1ef16d7ce70676a638fe077527efd22fc883a449489f9e472774eb51b1ed5
Tx public key: 8ab60afcc8e0bd45ea1a80c409446a24f876eaaf91813f92b3ab8287c5f99f0d
Timestamp: 1721370644 Timestamp [UCT]: 2024-07-19 06:30:44 Age [y:d:h:m:s]: 00:175:20:21:50
Block: 1068940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125791 RingCT/type: yes/0
Extra: 018ab60afcc8e0bd45ea1a80c409446a24f876eaaf91813f92b3ab8287c5f99f0d02110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 157df7b728bfe5ab426757e759a70b950ce65ded8560a58c4875fc5bae2a6ee0 0.600000000000 1540167 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": 1068950, "vin": [ { "gen": { "height": 1068940 } } ], "vout": [ { "amount": 600000000, "target": { "key": "157df7b728bfe5ab426757e759a70b950ce65ded8560a58c4875fc5bae2a6ee0" } } ], "extra": [ 1, 138, 182, 10, 252, 200, 224, 189, 69, 234, 26, 128, 196, 9, 68, 106, 36, 248, 118, 234, 175, 145, 129, 63, 146, 179, 171, 130, 135, 197, 249, 159, 13, 2, 17, 0, 0, 0, 11, 145, 225, 60, 4, 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