Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ce8a721db40a4a895706a27b349f7e58eefedb5d7fd2fe9d9d2e325e119b037

Tx prefix hash: 9a38227cdb63cf3fbea5b30d4dbd9dc2a52a19acf94cd1ca169de949442a2dc8
Tx public key: 42d4a90e2a468d1e367f695c2154d3e8db16d0d13e51ccaa24f8e40756e42e3e
Timestamp: 1717331427 Timestamp [UCT]: 2024-06-02 12:30:27 Age [y:d:h:m:s]: 00:326:00:13:27
Block: 1035445 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232994 RingCT/type: yes/0
Extra: 0142d4a90e2a468d1e367f695c2154d3e8db16d0d13e51ccaa24f8e40756e42e3e0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40d8f0f52954b13237b62a607833b396b3330a0e295876847f8d24bbe83d9a33 0.600000000000 1503966 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": 1035455, "vin": [ { "gen": { "height": 1035445 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40d8f0f52954b13237b62a607833b396b3330a0e295876847f8d24bbe83d9a33" } } ], "extra": [ 1, 66, 212, 169, 14, 42, 70, 141, 30, 54, 127, 105, 92, 33, 84, 211, 232, 219, 22, 208, 209, 62, 81, 204, 170, 36, 248, 228, 7, 86, 228, 46, 62, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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