Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1906776ab7c61af1294e69a1bba33792a615baa0c98342df00f22dbccb7f710

Tx prefix hash: 33820cf0b3cab35ecd97020ac9bec8b55de7196a3c9316ea5d2d200318ab8884
Tx public key: 7400c2033dbf484d13f2ce5e4fd50ddcabda2ae3b1060d96a65f3ffa10fba070
Timestamp: 1733507148 Timestamp [UCT]: 2024-12-06 17:45:48 Age [y:d:h:m:s]: 00:103:20:56:57
Block: 1169437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74055 RingCT/type: yes/0
Extra: 017400c2033dbf484d13f2ce5e4fd50ddcabda2ae3b1060d96a65f3ffa10fba0700211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4509e80d7fe177f2c0a4c1eae0c9989b404b01775e18d68dcdb41e0ce398f74 0.600000000000 1655154 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": 1169447, "vin": [ { "gen": { "height": 1169437 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4509e80d7fe177f2c0a4c1eae0c9989b404b01775e18d68dcdb41e0ce398f74" } } ], "extra": [ 1, 116, 0, 194, 3, 61, 191, 72, 77, 19, 242, 206, 94, 79, 213, 13, 220, 171, 218, 42, 227, 177, 6, 13, 150, 166, 95, 63, 250, 16, 251, 160, 112, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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