Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c9163d02cb38efe1e9c23f6772f018cdd84a158948e2b79ffadd29708d92017

Tx prefix hash: dc369bcee40c4a62fdb623fbfd5bcf27b37d049ecaaf9378c2ab629bea042938
Tx public key: c46e8a67b8368572a329ed8d1650baa9e9f757f8eb4fe459384dec4962281ab0
Timestamp: 1612455320 Timestamp [UCT]: 2021-02-04 16:15:20 Age [y:d:h:m:s]: 04:028:08:37:22
Block: 191988 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1039612 RingCT/type: yes/0
Extra: 01c46e8a67b8368572a329ed8d1650baa9e9f757f8eb4fe459384dec4962281ab002110000003b4ea414e5000000000000000000

1 output(s) for total of 141.868117357000 dcy

stealth address amount amount idx
00: 8e7263a31a1112ac7ab6b1007e2353fce72a87218a17fd50e91e5ebf1fd66d41 141.868117357000 386734 of 0

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": 191998, "vin": [ { "gen": { "height": 191988 } } ], "vout": [ { "amount": 141868117357, "target": { "key": "8e7263a31a1112ac7ab6b1007e2353fce72a87218a17fd50e91e5ebf1fd66d41" } } ], "extra": [ 1, 196, 110, 138, 103, 184, 54, 133, 114, 163, 41, 237, 141, 22, 80, 186, 169, 233, 247, 87, 248, 235, 79, 228, 89, 56, 77, 236, 73, 98, 40, 26, 176, 2, 17, 0, 0, 0, 59, 78, 164, 20, 229, 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