Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cadb6edad0f532b90b8880e9fff93dee9ddc3150a86711c7d9ff75e7c568c37e

Tx prefix hash: bb250c9441b806b96271933d78a93fc033c3bb83b9d5a5854b7cb976f5682e06
Tx public key: 26116461ff66fb3dd7a17511305ee12d882f071447fcfb409f7ad067dc5a548a
Timestamp: 1717083440 Timestamp [UCT]: 2024-05-30 15:37:20 Age [y:d:h:m:s]: 00:330:03:05:00
Block: 1033378 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235958 RingCT/type: yes/0
Extra: 0126116461ff66fb3dd7a17511305ee12d882f071447fcfb409f7ad067dc5a548a0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dfc62a88d9ae3397e4d9b67ded94313042049aee6b13d81d82cd0f31f8e1d788 0.600000000000 1501843 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": 1033388, "vin": [ { "gen": { "height": 1033378 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dfc62a88d9ae3397e4d9b67ded94313042049aee6b13d81d82cd0f31f8e1d788" } } ], "extra": [ 1, 38, 17, 100, 97, 255, 102, 251, 61, 215, 161, 117, 17, 48, 94, 225, 45, 136, 47, 7, 20, 71, 252, 251, 64, 159, 122, 208, 103, 220, 90, 84, 138, 2, 17, 0, 0, 0, 6, 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