Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 733027e36a2c490ec2afa8b4f671ff02efa3ce99af5b6dbd52e30c6d095ba826

Tx prefix hash: b3c5dbc44dfd47dd806adc0737a4282d9e0046c8586265043569b0bdeaff29ea
Tx public key: 39f7fc12a260dbbd58017dae1eda5ca673d6ac225495cddea583fb3a90ee9de9
Timestamp: 1764269017 Timestamp [UCT]: 2025-11-27 18:43:37 Age [y:d:h:m:s]: 00:026:09:09:32
Block: 1421448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18870 RingCT/type: yes/0
Extra: 0139f7fc12a260dbbd58017dae1eda5ca673d6ac225495cddea583fb3a90ee9de9021100000004d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12dff2e6be4d9cbb5227f416e3d119463f08ec3eaa090276dc4fb3b7a82a1beb 0.600000000000 1910005 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": 1421458, "vin": [ { "gen": { "height": 1421448 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12dff2e6be4d9cbb5227f416e3d119463f08ec3eaa090276dc4fb3b7a82a1beb" } } ], "extra": [ 1, 57, 247, 252, 18, 162, 96, 219, 189, 88, 1, 125, 174, 30, 218, 92, 166, 115, 214, 172, 34, 84, 149, 205, 222, 165, 131, 251, 58, 144, 238, 157, 233, 2, 17, 0, 0, 0, 4, 214, 225, 157, 124, 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