Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10f043e935726e3a7a9285684bc50c92bed9417239c99c4075abcd0fa3cbf3c5

Tx prefix hash: 090cc7f16c0dfbfa72a7669901048055b2ec77a56150dd06587b0acd6e8eeab8
Tx public key: 1cd30c9ec0d054e7b4072eb82d292b012775fcf9aebc934eb982b196d8be485d
Timestamp: 1581949425 Timestamp [UCT]: 2020-02-17 14:23:45 Age [y:d:h:m:s]: 04:315:05:49:12
Block: 66857 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1117663 RingCT/type: yes/0
Extra: 011cd30c9ec0d054e7b4072eb82d292b012775fcf9aebc934eb982b196d8be485d02110000000356c366d3000000000000000000

1 output(s) for total of 368.532517267000 dcy

stealth address amount amount idx
00: b6872f6a6a4cd23367081895ddbd0d9faa1435af4a005b1048754d6739037428 368.532517267000 123080 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": 66867, "vin": [ { "gen": { "height": 66857 } } ], "vout": [ { "amount": 368532517267, "target": { "key": "b6872f6a6a4cd23367081895ddbd0d9faa1435af4a005b1048754d6739037428" } } ], "extra": [ 1, 28, 211, 12, 158, 192, 208, 84, 231, 180, 7, 46, 184, 45, 41, 43, 1, 39, 117, 252, 249, 174, 188, 147, 78, 185, 130, 177, 150, 216, 190, 72, 93, 2, 17, 0, 0, 0, 3, 86, 195, 102, 211, 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