Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd554a58b3e7aa80973608047a06df2967d3752bdd3db1d652759c2c54609540

Tx prefix hash: a7703b942702aa16a7f9abe9871c7cb89a2427452b96ffec80abd85adb8d513b
Tx public key: e6697198e8eea2e521240f4cf1b93c53322e8cbd54a65344a459780e05056348
Timestamp: 1662507843 Timestamp [UCT]: 2022-09-06 23:44:03 Age [y:d:h:m:s]: 02:194:22:30:57
Block: 582381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 660616 RingCT/type: yes/0
Extra: 01e6697198e8eea2e521240f4cf1b93c53322e8cbd54a65344a459780e05056348021100000007e4c64a6f000000000000000000

1 output(s) for total of 7.216557461000 dcy

stealth address amount amount idx
00: 0d54c63e2493dd45f8311e6bf1e045af83b9eea3f77e265808a6674f1afeb6e1 7.216557461000 1016123 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": 582391, "vin": [ { "gen": { "height": 582381 } } ], "vout": [ { "amount": 7216557461, "target": { "key": "0d54c63e2493dd45f8311e6bf1e045af83b9eea3f77e265808a6674f1afeb6e1" } } ], "extra": [ 1, 230, 105, 113, 152, 232, 238, 162, 229, 33, 36, 15, 76, 241, 185, 60, 83, 50, 46, 140, 189, 84, 166, 83, 68, 164, 89, 120, 14, 5, 5, 99, 72, 2, 17, 0, 0, 0, 7, 228, 198, 74, 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