Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f461d5db4b1e3b9c987fb32e01141bbf2e506badb01bbbca2a29475d9bd141ff

Tx prefix hash: 672239093a5690025610a95f5069b85d35a162de1bc70ef8130f1f3b9978bce6
Tx public key: e4ca87416b8aa2a0fd4645861d78479db193b13885e8f54502fc85f7dd811d46
Timestamp: 1745670508 Timestamp [UCT]: 2025-04-26 12:28:28 Age [y:d:h:m:s]: 00:209:03:27:10
Block: 1269872 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147171 RingCT/type: yes/0
Extra: 01e4ca87416b8aa2a0fd4645861d78479db193b13885e8f54502fc85f7dd811d46021100000019dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49eb36dcf8de9a780d78da4e2ff2fc005d4c07dec66af4b57dafc1bd5ce5c1b5 0.600000000000 1757111 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": 1269882, "vin": [ { "gen": { "height": 1269872 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49eb36dcf8de9a780d78da4e2ff2fc005d4c07dec66af4b57dafc1bd5ce5c1b5" } } ], "extra": [ 1, 228, 202, 135, 65, 107, 138, 162, 160, 253, 70, 69, 134, 29, 120, 71, 157, 177, 147, 177, 56, 133, 232, 245, 69, 2, 252, 133, 247, 221, 129, 29, 70, 2, 17, 0, 0, 0, 25, 219, 181, 113, 193, 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