Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a998c27f7aa272cc72633ffb5e9e4fcf5c7350560e73281c504abda47376489f

Tx prefix hash: 7cfc4139070d568df2023cdc02e4e4eec976e35e0cd0351ba38c7d0b5f6a0763
Tx public key: 56a21bea0bb70d0326c5cd7550d848779cc9da0cb98e7121752dbdc751f0624d
Timestamp: 1737748170 Timestamp [UCT]: 2025-01-24 19:49:30 Age [y:d:h:m:s]: 00:144:06:13:47
Block: 1204495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102846 RingCT/type: yes/0
Extra: 0156a21bea0bb70d0326c5cd7550d848779cc9da0cb98e7121752dbdc751f0624d021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39ae62a31be8231741e8e648a78e7dddea4c260bf8199110f4aee8da14d45851 0.600000000000 1691182 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": 1204505, "vin": [ { "gen": { "height": 1204495 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39ae62a31be8231741e8e648a78e7dddea4c260bf8199110f4aee8da14d45851" } } ], "extra": [ 1, 86, 162, 27, 234, 11, 183, 13, 3, 38, 197, 205, 117, 80, 216, 72, 119, 156, 201, 218, 12, 185, 142, 113, 33, 117, 45, 189, 199, 81, 240, 98, 77, 2, 17, 0, 0, 0, 6, 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