Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e5747f3126f109d4eb9fa043ee88de700a88459dd50f2dbf204f4c3084fa5b4

Tx prefix hash: 4851eef2b2f9b525031a89d8fced8786d1cf7c8594f827be588f1b626cb52afd
Tx public key: 14b7ef29993353bb579517cf5ea9571f1f629c18cdfebc5b00a5dad036e728da
Timestamp: 1734308861 Timestamp [UCT]: 2024-12-16 00:27:41 Age [y:d:h:m:s]: 00:092:17:35:36
Block: 1176095 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66051 RingCT/type: yes/0
Extra: 0114b7ef29993353bb579517cf5ea9571f1f629c18cdfebc5b00a5dad036e728da02110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 535ad78f78e0ea5a91af26b107c0504acfdcaa4d56be3b5c2874e32fc6329609 0.600000000000 1662424 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": 1176105, "vin": [ { "gen": { "height": 1176095 } } ], "vout": [ { "amount": 600000000, "target": { "key": "535ad78f78e0ea5a91af26b107c0504acfdcaa4d56be3b5c2874e32fc6329609" } } ], "extra": [ 1, 20, 183, 239, 41, 153, 51, 83, 187, 87, 149, 23, 207, 94, 169, 87, 31, 31, 98, 156, 24, 205, 254, 188, 91, 0, 165, 218, 208, 54, 231, 40, 218, 2, 17, 0, 0, 0, 11, 0, 127, 151, 138, 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