Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b49a2338eadd15fbf44097c6c409f48b16c53e82f7da567efc813611a52fa115

Tx prefix hash: 9c8f0fe9b9ea7ec2ee0f187172c0ebe402a5351a60c2cedd52a079bdc767cce0
Tx public key: 7206899e4f6b64b01dac931458c50d6eba1a5d34bc769a59473c331154174e08
Timestamp: 1737698015 Timestamp [UCT]: 2025-01-24 05:53:35 Age [y:d:h:m:s]: 00:150:12:14:55
Block: 1204084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107202 RingCT/type: yes/0
Extra: 017206899e4f6b64b01dac931458c50d6eba1a5d34bc769a59473c331154174e08021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 947e8c6b4a7006a56bb0a06edf8e92b18725ca77e045ec79afd77d603c84d2d3 0.600000000000 1690767 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": 1204094, "vin": [ { "gen": { "height": 1204084 } } ], "vout": [ { "amount": 600000000, "target": { "key": "947e8c6b4a7006a56bb0a06edf8e92b18725ca77e045ec79afd77d603c84d2d3" } } ], "extra": [ 1, 114, 6, 137, 158, 79, 107, 100, 176, 29, 172, 147, 20, 88, 197, 13, 110, 186, 26, 93, 52, 188, 118, 154, 89, 71, 60, 51, 17, 84, 23, 78, 8, 2, 17, 0, 0, 0, 7, 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