Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43495f1ec5b1be28176770fd347db70587a44bf6dd24c8277dd4edf97cabb1bb

Tx prefix hash: b105d4cb25dde9dbc3e3102a11d08aeaf73b36ee6cffb14c815c71d4125dcce8
Tx public key: 09993b1fcd5b50e53ead2cb03f2cf74a651717e0385ec25d12b3fd0bd7bdb1e9
Timestamp: 1608647130 Timestamp [UCT]: 2020-12-22 14:25:30 Age [y:d:h:m:s]: 04:164:02:16:59
Block: 167134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1130047 RingCT/type: yes/0
Extra: 0109993b1fcd5b50e53ead2cb03f2cf74a651717e0385ec25d12b3fd0bd7bdb1e90211000000a0df1e48bb000000000000000000

1 output(s) for total of 171.481134212000 dcy

stealth address amount amount idx
00: a222c10efe4efd308c3d0d2bd440a07922ea324b254b4a3f0807e1710bd06b16 171.481134212000 307573 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": 167144, "vin": [ { "gen": { "height": 167134 } } ], "vout": [ { "amount": 171481134212, "target": { "key": "a222c10efe4efd308c3d0d2bd440a07922ea324b254b4a3f0807e1710bd06b16" } } ], "extra": [ 1, 9, 153, 59, 31, 205, 91, 80, 229, 62, 173, 44, 176, 63, 44, 247, 74, 101, 23, 23, 224, 56, 94, 194, 93, 18, 179, 253, 11, 215, 189, 177, 233, 2, 17, 0, 0, 0, 160, 223, 30, 72, 187, 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