Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1023e3dfa96d72bc13d53ddb08917338b8705c3d1d29b33c209336b5cb4b2b1

Tx prefix hash: aafbee276dd84bc51b1c73acb4d2ce292f46bea68f06e8ca40ab8a9e708fb8f0
Tx public key: 345ae89542a48fe5af419e674aa48ce93047fcdde5c4adcc4c38d4ae73f285ad
Timestamp: 1735853455 Timestamp [UCT]: 2025-01-02 21:30:55 Age [y:d:h:m:s]: 00:322:20:13:32
Block: 1188857 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228243 RingCT/type: yes/0
Extra: 01345ae89542a48fe5af419e674aa48ce93047fcdde5c4adcc4c38d4ae73f285ad021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a7a1f8a793d88d238789cb5f1bded38f9cca79fb2d4674861a2ff0e5843ce6b 0.600000000000 1675362 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": 1188867, "vin": [ { "gen": { "height": 1188857 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a7a1f8a793d88d238789cb5f1bded38f9cca79fb2d4674861a2ff0e5843ce6b" } } ], "extra": [ 1, 52, 90, 232, 149, 66, 164, 143, 229, 175, 65, 158, 103, 74, 164, 140, 233, 48, 71, 252, 221, 229, 196, 173, 204, 76, 56, 212, 174, 115, 242, 133, 173, 2, 17, 0, 0, 0, 1, 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