Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d90b8831fc57c33ef92880addcc493eef722cd25f88296e9dd6e3c781748b27

Tx prefix hash: 9dcea7d6383ba2e2cc3e93ceb55a0a5a79084dd5fd765fe2d4895956159323b1
Tx public key: 7f69f5402f2b01561b78b0197d63e7b90bd89e68fb2622c9dd22d3c65e402cf2
Timestamp: 1736316734 Timestamp [UCT]: 2025-01-08 06:12:14 Age [y:d:h:m:s]: 00:163:14:53:36
Block: 1192693 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116614 RingCT/type: yes/0
Extra: 017f69f5402f2b01561b78b0197d63e7b90bd89e68fb2622c9dd22d3c65e402cf20211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc8ae7dc9f0bb40f2618dbbe81cfbabb1cc490cad6a57ad9484bd5061e6616c0 0.600000000000 1679248 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": 1192703, "vin": [ { "gen": { "height": 1192693 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc8ae7dc9f0bb40f2618dbbe81cfbabb1cc490cad6a57ad9484bd5061e6616c0" } } ], "extra": [ 1, 127, 105, 245, 64, 47, 43, 1, 86, 27, 120, 176, 25, 125, 99, 231, 185, 11, 216, 158, 104, 251, 38, 34, 201, 221, 34, 211, 198, 94, 64, 44, 242, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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