Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 784a7da2ff969f906ea0e244a7be9b290c220de3dba67158ae19013b4a1aff80

Tx prefix hash: f2ad06a4a2744d4fb56858b5c451641e25098f6b4561ebfef4c11dfcdec89ec8
Tx public key: afa9ab153ad0e7fc048236d23102b057ef3e6208b316660fa917423b6c917605
Timestamp: 1704507970 Timestamp [UCT]: 2024-01-06 02:26:10 Age [y:d:h:m:s]: 01:308:17:14:43
Block: 929094 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 479489 RingCT/type: yes/0
Extra: 01afa9ab153ad0e7fc048236d23102b057ef3e6208b316660fa917423b6c91760502110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ceb0c0f5cca475037f293a209a9608021ffc6aecf51c52d9c9fd383e6b9a20d0 0.600000000000 1386962 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": 929104, "vin": [ { "gen": { "height": 929094 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ceb0c0f5cca475037f293a209a9608021ffc6aecf51c52d9c9fd383e6b9a20d0" } } ], "extra": [ 1, 175, 169, 171, 21, 58, 208, 231, 252, 4, 130, 54, 210, 49, 2, 176, 87, 239, 62, 98, 8, 179, 22, 102, 15, 169, 23, 66, 59, 108, 145, 118, 5, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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