Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e63ea41c895e11a581b66508a77288a0c94925311d9b0232a58f787caf552fb

Tx prefix hash: ef495a8eb960b3fd885ada840f793c998d7e4267d28138ab5ae2bc3b0fdea176
Tx public key: 79d27f8a7f9d334f48bde8f63e364c182fb6a0ecae7bc2f44b9dfa45cb993b65
Timestamp: 1725912532 Timestamp [UCT]: 2024-09-09 20:08:52 Age [y:d:h:m:s]: 00:212:15:02:09
Block: 1106580 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151797 RingCT/type: yes/0
Extra: 0179d27f8a7f9d334f48bde8f63e364c182fb6a0ecae7bc2f44b9dfa45cb993b65021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d318f17605555fa276e4b3fb2f1fe77dc5865084f2147f6e57d9369138c253e0 0.600000000000 1584181 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": 1106590, "vin": [ { "gen": { "height": 1106580 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d318f17605555fa276e4b3fb2f1fe77dc5865084f2147f6e57d9369138c253e0" } } ], "extra": [ 1, 121, 210, 127, 138, 127, 157, 51, 79, 72, 189, 232, 246, 62, 54, 76, 24, 47, 182, 160, 236, 174, 123, 194, 244, 75, 157, 250, 69, 203, 153, 59, 101, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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