Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e4fb413b2e7fb0d2fa86e5b36b1e306247ffac1c2a3bfd3821f2c61e897e3dd

Tx prefix hash: e3df7cabf0f38cb7cf120d968bd1748e83cffb425188d3999de16b9cf57d9829
Tx public key: ac1f9498aaf81cbf647c1f527f40dc2f91a6f3b7bbfabc607471a66edf9a4d97
Timestamp: 1732685291 Timestamp [UCT]: 2024-11-27 05:28:11 Age [y:d:h:m:s]: 00:124:08:33:32
Block: 1162627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88681 RingCT/type: yes/0
Extra: 01ac1f9498aaf81cbf647c1f527f40dc2f91a6f3b7bbfabc607471a66edf9a4d970211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f5128e7dcb179535f704b459f1a4eb48f168d30be9fea12b55de44448124e02 0.600000000000 1648284 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": 1162637, "vin": [ { "gen": { "height": 1162627 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f5128e7dcb179535f704b459f1a4eb48f168d30be9fea12b55de44448124e02" } } ], "extra": [ 1, 172, 31, 148, 152, 170, 248, 28, 191, 100, 124, 31, 82, 127, 64, 220, 47, 145, 166, 243, 183, 187, 250, 188, 96, 116, 113, 166, 110, 223, 154, 77, 151, 2, 17, 0, 0, 0, 1, 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