Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3eb459026e989705d3387b584d51e75e7cf4e0c586c19d2162b96c2c1e749697

Tx prefix hash: cc240b5c814cdb121b2ac645d47e61e139ff0fde594a056e5f55a828d496bebb
Tx public key: dddcb0f8c676ee37b92f851222a5da85a98608ec4b5a672ef45853249d09073d
Timestamp: 1697082287 Timestamp [UCT]: 2023-10-12 03:44:47 Age [y:d:h:m:s]: 01:096:13:26:48
Block: 867762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330252 RingCT/type: yes/0
Extra: 01dddcb0f8c676ee37b92f851222a5da85a98608ec4b5a672ef45853249d09073d021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.817983041000 dcy

stealth address amount amount idx
00: c0002590e8d34255d0c05d60cf6529e17d8d47a08331201430fcb9a7f6f1b977 0.817983041000 1322478 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": 867772, "vin": [ { "gen": { "height": 867762 } } ], "vout": [ { "amount": 817983041, "target": { "key": "c0002590e8d34255d0c05d60cf6529e17d8d47a08331201430fcb9a7f6f1b977" } } ], "extra": [ 1, 221, 220, 176, 248, 198, 118, 238, 55, 185, 47, 133, 18, 34, 165, 218, 133, 169, 134, 8, 236, 75, 90, 103, 46, 244, 88, 83, 36, 157, 9, 7, 61, 2, 17, 0, 0, 0, 2, 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