Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35930222b00027a0557efa1347c2ba8ec096b1918a8cb2c9db2e5ac6fbe72a48

Tx prefix hash: ce9adf294cd8c312a220b6d8ae388e1350cfc487731a47a4f6aa366836d49c46
Tx public key: 2365fe37164aa4ea5f825bf011e584cd9fe0505a1efc8a862cb7b7ee93f779cf
Timestamp: 1701024620 Timestamp [UCT]: 2023-11-26 18:50:20 Age [y:d:h:m:s]: 01:051:21:28:29
Block: 900230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298480 RingCT/type: yes/0
Extra: 012365fe37164aa4ea5f825bf011e584cd9fe0505a1efc8a862cb7b7ee93f779cf021100000010faf35c9c000000000000000000

1 output(s) for total of 0.638504981000 dcy

stealth address amount amount idx
00: 4d64cf041d7acbf3f9330757c12d17d734efc95b12a28fa96e0c0c4570c77a02 0.638504981000 1356717 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": 900240, "vin": [ { "gen": { "height": 900230 } } ], "vout": [ { "amount": 638504981, "target": { "key": "4d64cf041d7acbf3f9330757c12d17d734efc95b12a28fa96e0c0c4570c77a02" } } ], "extra": [ 1, 35, 101, 254, 55, 22, 74, 164, 234, 95, 130, 91, 240, 17, 229, 132, 205, 159, 224, 80, 90, 30, 252, 138, 134, 44, 183, 183, 238, 147, 247, 121, 207, 2, 17, 0, 0, 0, 16, 250, 243, 92, 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