Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 325627fd38a7a407f75f5396d5389cd45d12a62e8db66765583568e89689fbfa

Tx prefix hash: 765bbbd64b01632d2be8080bc46928415520e57c403cb7c9e066cbe126aad170
Tx public key: a4f2944a6ff9a5b415e1d17dc2266fd87e9b4fef7377200a40887bf5845dc642
Timestamp: 1682195440 Timestamp [UCT]: 2023-04-22 20:30:40 Age [y:d:h:m:s]: 01:308:00:22:16
Block: 744383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 481365 RingCT/type: yes/0
Extra: 01a4f2944a6ff9a5b415e1d17dc2266fd87e9b4fef7377200a40887bf5845dc642021100000003b3164c24000000000000000000

1 output(s) for total of 2.096767731000 dcy

stealth address amount amount idx
00: d0a6582214d0f9fa126c388df5df20b6f19d88ce466934cf3b78fc2d892df490 2.096767731000 1191700 of 0

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": 744393, "vin": [ { "gen": { "height": 744383 } } ], "vout": [ { "amount": 2096767731, "target": { "key": "d0a6582214d0f9fa126c388df5df20b6f19d88ce466934cf3b78fc2d892df490" } } ], "extra": [ 1, 164, 242, 148, 74, 111, 249, 165, 180, 21, 225, 209, 125, 194, 38, 111, 216, 126, 155, 79, 239, 115, 119, 32, 10, 64, 136, 123, 245, 132, 93, 198, 66, 2, 17, 0, 0, 0, 3, 179, 22, 76, 36, 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