Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7909d51f445c34246b4c89af52af0035931e10cb7ea509d18a81357cfb13dc8

Tx prefix hash: e475c5f31bbb56004d094de1feb63d2131b15841ed90964c8ab7bc3e2ad3bc08
Tx public key: 937174cb15ab82d69edb6577e6c36073eadd3e9284d1e4aa51dba3ef94e9e3b4
Timestamp: 1704914232 Timestamp [UCT]: 2024-01-10 19:17:12 Age [y:d:h:m:s]: 01:090:03:03:17
Block: 932474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325513 RingCT/type: yes/0
Extra: 01937174cb15ab82d69edb6577e6c36073eadd3e9284d1e4aa51dba3ef94e9e3b40211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 033e586f10b1f5de0f3edeafd57bad0bc7ef932304dbd57ee94dcc96f0b83620 0.600000000000 1390410 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": 932484, "vin": [ { "gen": { "height": 932474 } } ], "vout": [ { "amount": 600000000, "target": { "key": "033e586f10b1f5de0f3edeafd57bad0bc7ef932304dbd57ee94dcc96f0b83620" } } ], "extra": [ 1, 147, 113, 116, 203, 21, 171, 130, 214, 158, 219, 101, 119, 230, 195, 96, 115, 234, 221, 62, 146, 132, 209, 228, 170, 81, 219, 163, 239, 148, 233, 227, 180, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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