Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1dfc45d46ab9cc60618b67b6a0d8d690efdc8e4afd7dcdbac945546caf104133

Tx prefix hash: 7204be41ea2d8f0bc6d9fe2a439da88b10bc5dd74d8d4042954510645051df4d
Tx public key: e50c3bf6c8d9945981df0a9e04c2343dbc2c9f59d5466d44f0ebee5567baf4c8
Timestamp: 1637554392 Timestamp [UCT]: 2021-11-22 04:13:12 Age [y:d:h:m:s]: 03:157:08:50:20
Block: 379436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 891166 RingCT/type: yes/0
Extra: 01e50c3bf6c8d9945981df0a9e04c2343dbc2c9f59d5466d44f0ebee5567baf4c8021100000025e9564d6f000000000000000000

1 output(s) for total of 33.944655246000 dcy

stealth address amount amount idx
00: 38bbc5eee45b33fa891496be550dcd2a2aa3dcd9a30323f11e2a7e019014be8a 33.944655246000 767008 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": 379446, "vin": [ { "gen": { "height": 379436 } } ], "vout": [ { "amount": 33944655246, "target": { "key": "38bbc5eee45b33fa891496be550dcd2a2aa3dcd9a30323f11e2a7e019014be8a" } } ], "extra": [ 1, 229, 12, 59, 246, 200, 217, 148, 89, 129, 223, 10, 158, 4, 194, 52, 61, 188, 44, 159, 89, 213, 70, 109, 68, 240, 235, 238, 85, 103, 186, 244, 200, 2, 17, 0, 0, 0, 37, 233, 86, 77, 111, 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