Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 998a0f1d09c1477b5e36448803dcedc92da1832c60e62ef0b0c7e461ef590c2e

Tx prefix hash: 2dac2d17a0196d40d1130617bc620244fa6612e8e7bdaabbf1bfb12be025c4b1
Tx public key: 2c9f593bc9cef1be3936ac39f816fb7dbd061f73734a17ad204cb569b7a7ede5
Timestamp: 1728848191 Timestamp [UCT]: 2024-10-13 19:36:31 Age [y:d:h:m:s]: 00:175:06:11:50
Block: 1130913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125024 RingCT/type: yes/0
Extra: 012c9f593bc9cef1be3936ac39f816fb7dbd061f73734a17ad204cb569b7a7ede502110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be7da223712d2e36310d923368ac766e207809717ea3c0ea6bd2801d608ffae7 0.600000000000 1613794 of 15

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": 1130923, "vin": [ { "gen": { "height": 1130913 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be7da223712d2e36310d923368ac766e207809717ea3c0ea6bd2801d608ffae7" } } ], "extra": [ 1, 44, 159, 89, 59, 201, 206, 241, 190, 57, 54, 172, 57, 248, 22, 251, 125, 189, 6, 31, 115, 115, 74, 23, 173, 32, 76, 181, 105, 183, 167, 237, 229, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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