Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdd8f1bc8dbb5524b4bbbd521757d93b8df2a112f58be13dea582675ed5cf6ec

Tx prefix hash: 349d00d066c5fe63749749df6ccc6714fbdfbb92c40970c392feacb78dc727d1
Tx public key: 2bd19655e39c9c62f05cf723305bee0fafc45297e96fd46d0747fc2c3a99c003
Timestamp: 1702361052 Timestamp [UCT]: 2023-12-12 06:04:12 Age [y:d:h:m:s]: 01:160:23:28:54
Block: 911319 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376230 RingCT/type: yes/0
Extra: 012bd19655e39c9c62f05cf723305bee0fafc45297e96fd46d0747fc2c3a99c003021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34e65dc5334387709e6f1ad8702f6a7fab1fce9e1b59eb79cdc0574aa2d2190f 0.600000000000 1368500 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": 911329, "vin": [ { "gen": { "height": 911319 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34e65dc5334387709e6f1ad8702f6a7fab1fce9e1b59eb79cdc0574aa2d2190f" } } ], "extra": [ 1, 43, 209, 150, 85, 227, 156, 156, 98, 240, 92, 247, 35, 48, 91, 238, 15, 175, 196, 82, 151, 233, 111, 212, 109, 7, 71, 252, 44, 58, 153, 192, 3, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 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