Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42e03ba5deae10f4717bfb225337a6364cb57c3e475a1805f1f3b9f90751bdd7

Tx prefix hash: 922a6862c77fb9c2f4481a5006b010980e9a216b4d37ab18dfc9fcf23cad1a4f
Tx public key: 8513146bb2d03e07291574f7671b8f6837f7da872bb580dd733d42fb9379af03
Timestamp: 1742066230 Timestamp [UCT]: 2025-03-15 19:17:10 Age [y:d:h:m:s]: 00:058:05:40:54
Block: 1240041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41631 RingCT/type: yes/0
Extra: 018513146bb2d03e07291574f7671b8f6837f7da872bb580dd733d42fb9379af030211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4a66d8b83d83e951bb0c7aba5bb546ca56553491369ff0d56f475ef7b21f60b 0.600000000000 1727006 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": 1240051, "vin": [ { "gen": { "height": 1240041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4a66d8b83d83e951bb0c7aba5bb546ca56553491369ff0d56f475ef7b21f60b" } } ], "extra": [ 1, 133, 19, 20, 107, 178, 208, 62, 7, 41, 21, 116, 247, 103, 27, 143, 104, 55, 247, 218, 135, 43, 181, 128, 221, 115, 61, 66, 251, 147, 121, 175, 3, 2, 17, 0, 0, 0, 4, 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