Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3615846a3699c70f817a57e1678332892cbbd2a76d13db0930d4367f9fd7441e

Tx prefix hash: 11d56af908a897799527cf071d4f322f57b7ff940dd0161874789babe153013a
Tx public key: 94b2f35fb93c618284086c51c2aa7480a1c625e82976097df2c4662d4471b3de
Timestamp: 1705687693 Timestamp [UCT]: 2024-01-19 18:08:13 Age [y:d:h:m:s]: 01:301:10:22:52
Block: 938872 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 474267 RingCT/type: yes/0
Extra: 0194b2f35fb93c618284086c51c2aa7480a1c625e82976097df2c4662d4471b3de0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b7958d709e1c6fe4c4073b03c30a440d06589717699d21258221e415252cec5 0.600000000000 1396954 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": 938882, "vin": [ { "gen": { "height": 938872 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b7958d709e1c6fe4c4073b03c30a440d06589717699d21258221e415252cec5" } } ], "extra": [ 1, 148, 178, 243, 95, 185, 60, 97, 130, 132, 8, 108, 81, 194, 170, 116, 128, 161, 198, 37, 232, 41, 118, 9, 125, 242, 196, 102, 45, 68, 113, 179, 222, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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