Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 232f14cf33438795517c77cf1c25b3cc54b9767300d655e9dac3de8e8c14ec25

Tx prefix hash: b66f73019dc1bec967e61aa8e4c2e497f5bfe8ba366ea75b2ae992b55e1a5107
Tx public key: 64b51c3d84ad6b594774fffc03b4d316c1d52d6d6da3280ac8ac343c9a305ae7
Timestamp: 1577797963 Timestamp [UCT]: 2019-12-31 13:12:43 Age [y:d:h:m:s]: 05:003:06:50:17
Block: 35761 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1152331 RingCT/type: yes/0
Extra: 0164b51c3d84ad6b594774fffc03b4d316c1d52d6d6da3280ac8ac343c9a305ae70211000000044943cd9f000000000000000000

1 output(s) for total of 467.207510686000 dcy

stealth address amount amount idx
00: 3174e1872638ef9ab69fe751ff9b65258ec3d6024f15cb58c4e5b4d3939a59d5 467.207510686000 60389 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": 35771, "vin": [ { "gen": { "height": 35761 } } ], "vout": [ { "amount": 467207510686, "target": { "key": "3174e1872638ef9ab69fe751ff9b65258ec3d6024f15cb58c4e5b4d3939a59d5" } } ], "extra": [ 1, 100, 181, 28, 61, 132, 173, 107, 89, 71, 116, 255, 252, 3, 180, 211, 22, 193, 213, 45, 109, 109, 163, 40, 10, 200, 172, 52, 60, 154, 48, 90, 231, 2, 17, 0, 0, 0, 4, 73, 67, 205, 159, 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