Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b9e9bb3ca1d1d0a34d7362a6f33c4e083d9251dc82c45f537995f61fc1d1f9b

Tx prefix hash: 769ec2a1067bb04398a89b77a1bcf2f3c35274a8f367f286141bd4b672cf9d10
Tx public key: 50a1bfc50147b882f83805f997702b319bda018e0df0e6669aec9985aacd352f
Timestamp: 1732183566 Timestamp [UCT]: 2024-11-21 10:06:06 Age [y:d:h:m:s]: 00:002:15:48:04
Block: 1158459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1919 RingCT/type: yes/0
Extra: 0150a1bfc50147b882f83805f997702b319bda018e0df0e6669aec9985aacd352f021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b3391c81797203001f7d1c58efe9f2585684ef67d044e299739d4825b7e78cf 0.600000000000 1644088 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": 1158469, "vin": [ { "gen": { "height": 1158459 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b3391c81797203001f7d1c58efe9f2585684ef67d044e299739d4825b7e78cf" } } ], "extra": [ 1, 80, 161, 191, 197, 1, 71, 184, 130, 248, 56, 5, 249, 151, 112, 43, 49, 155, 218, 1, 142, 13, 240, 230, 102, 154, 236, 153, 133, 170, 205, 53, 47, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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