Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: acb544a57f37c4c775368a76773260742686613bad64b8726e1238f53edb4688

Tx prefix hash: 06aff3e2c99f673cc96ac5a72cb1b6c71a61ed9d332638e39ad20acdc0375b4d
Tx public key: 7e2105b258b816d6807cd2b85d6dc730cb1f878373faf317e3b2eca587e3e50b
Timestamp: 1737429557 Timestamp [UCT]: 2025-01-21 03:19:17 Age [y:d:h:m:s]: 00:148:00:26:54
Block: 1201862 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105527 RingCT/type: yes/0
Extra: 017e2105b258b816d6807cd2b85d6dc730cb1f878373faf317e3b2eca587e3e50b0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f69261256db149b49552cd47d8d76b19d70b876e53902e577462cd7cb1e3113 0.600000000000 1688519 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": 1201872, "vin": [ { "gen": { "height": 1201862 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f69261256db149b49552cd47d8d76b19d70b876e53902e577462cd7cb1e3113" } } ], "extra": [ 1, 126, 33, 5, 178, 88, 184, 22, 214, 128, 124, 210, 184, 93, 109, 199, 48, 203, 31, 135, 131, 115, 250, 243, 23, 227, 178, 236, 165, 135, 227, 229, 11, 2, 17, 0, 0, 0, 3, 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