Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3faa94c7141ed19f46e820778a03c366a30e3f211c449251f7db265d38e7c1ec

Tx prefix hash: cf6acf9611bccae45db24b984990b61a856a79f0482399ab8f90088790c7610d
Tx public key: f0bd1ea1eabf969f83134972e533a6cb2dd2841cca96f051db13eeb7ebe2f022
Timestamp: 1668905776 Timestamp [UCT]: 2022-11-20 00:56:16 Age [y:d:h:m:s]: 02:177:00:31:27
Block: 634870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 648254 RingCT/type: yes/0
Extra: 01f0bd1ea1eabf969f83134972e533a6cb2dd2841cca96f051db13eeb7ebe2f02202110000000533af99f4000000000000000000

1 output(s) for total of 4.835174493000 dcy

stealth address amount amount idx
00: 274b62ccc34379639089056eeb60cf828fead01e1aa053d83b5dc752249e85c2 4.835174493000 1074059 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": 634880, "vin": [ { "gen": { "height": 634870 } } ], "vout": [ { "amount": 4835174493, "target": { "key": "274b62ccc34379639089056eeb60cf828fead01e1aa053d83b5dc752249e85c2" } } ], "extra": [ 1, 240, 189, 30, 161, 234, 191, 150, 159, 131, 19, 73, 114, 229, 51, 166, 203, 45, 210, 132, 28, 202, 150, 240, 81, 219, 19, 238, 183, 235, 226, 240, 34, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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