Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af2f1865ca9cd5ba0371cb7c64933ac29ef2e1fdb47e8b581fe694c4ebb9079f

Tx prefix hash: b562b6258224e7c73eef87e688fb1628a1f7ea409689c85070975143061da524
Tx public key: 9f205beff9df176930f99d111a0dc4f28f4665376a9f1e03e4e32c92012991dd
Timestamp: 1726063162 Timestamp [UCT]: 2024-09-11 13:59:22 Age [y:d:h:m:s]: 00:102:03:49:39
Block: 1107819 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73093 RingCT/type: yes/0
Extra: 019f205beff9df176930f99d111a0dc4f28f4665376a9f1e03e4e32c92012991dd021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9137169dbd05402fdd37cf599fed14adcb0cba51d877853911ba6e6eebbebee2 0.600000000000 1585498 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": 1107829, "vin": [ { "gen": { "height": 1107819 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9137169dbd05402fdd37cf599fed14adcb0cba51d877853911ba6e6eebbebee2" } } ], "extra": [ 1, 159, 32, 91, 239, 249, 223, 23, 105, 48, 249, 157, 17, 26, 13, 196, 242, 143, 70, 101, 55, 106, 159, 30, 3, 228, 227, 44, 146, 1, 41, 145, 221, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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