Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f8efd447fceb0fda6a44c52f419bbbfa8666951b761bea73d2e4ac7959832ec

Tx prefix hash: 775f2c212335f07609b9ea2cdb21fbdd975fc04149528f54ccee249acb7134df
Tx public key: ff74ef3d6ee82b6ebe014a51ab737c556bfe5822c4ef97781ac73d46b84a92b8
Timestamp: 1648518079 Timestamp [UCT]: 2022-03-29 01:41:19 Age [y:d:h:m:s]: 02:322:19:51:20
Block: 468596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 750045 RingCT/type: yes/0
Extra: 01ff74ef3d6ee82b6ebe014a51ab737c556bfe5822c4ef97781ac73d46b84a92b80211000000044a0f5013000000000000000000

1 output(s) for total of 17.192822522000 dcy

stealth address amount amount idx
00: 9d769f4c634d64695d5862990a69b8bbc81e9bf6273fb3c180a0f13e1ac76e6e 17.192822522000 887344 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": 468606, "vin": [ { "gen": { "height": 468596 } } ], "vout": [ { "amount": 17192822522, "target": { "key": "9d769f4c634d64695d5862990a69b8bbc81e9bf6273fb3c180a0f13e1ac76e6e" } } ], "extra": [ 1, 255, 116, 239, 61, 110, 232, 43, 110, 190, 1, 74, 81, 171, 115, 124, 85, 107, 254, 88, 34, 196, 239, 151, 120, 26, 199, 61, 70, 184, 74, 146, 184, 2, 17, 0, 0, 0, 4, 74, 15, 80, 19, 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