Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 579c3567902942e5da3efd90c233d66138252bb043a0be5ae3d31a80af2a6ddb

Tx prefix hash: 0bf20ac2804d0bdb6e4764af1e4a25ad8b803cb9bed411f6a2828e7b7ef22260
Tx public key: c2891551e40264e8eeeb78fe2faf6eba0b221d3d572a44631cf418f2e06a0ad8
Timestamp: 1703121940 Timestamp [UCT]: 2023-12-21 01:25:40 Age [y:d:h:m:s]: 02:039:11:57:06
Block: 917646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 547851 RingCT/type: yes/0
Extra: 01c2891551e40264e8eeeb78fe2faf6eba0b221d3d572a44631cf418f2e06a0ad8021100000002e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1c9b37b2ab10cecacdea8bb9466cbc541fc18fe38afbd9407894f48f1ec444e 0.600000000000 1375228 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": 917656, "vin": [ { "gen": { "height": 917646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1c9b37b2ab10cecacdea8bb9466cbc541fc18fe38afbd9407894f48f1ec444e" } } ], "extra": [ 1, 194, 137, 21, 81, 228, 2, 100, 232, 238, 235, 120, 254, 47, 175, 110, 186, 11, 34, 29, 61, 87, 42, 68, 99, 28, 244, 24, 242, 224, 106, 10, 216, 2, 17, 0, 0, 0, 2, 224, 133, 50, 182, 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