Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f97c7122cac9ef758917d6fa57ae74464a601f90eebe119a78c3cbf601f74fa3

Tx prefix hash: 903d7ef915d9e4f98c07f9198a958f3effbc62ddca3eaa2b1d57f026215261c0
Tx public key: 59ddbf87b05cfe331e40a18c52dbddd581e3853d6ae9b38f09915811235535cb
Timestamp: 1750003720 Timestamp [UCT]: 2025-06-15 16:08:40 Age [y:d:h:m:s]: 00:151:18:05:55
Block: 1305641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106238 RingCT/type: yes/0
Extra: 0159ddbf87b05cfe331e40a18c52dbddd581e3853d6ae9b38f09915811235535cb0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35aec8631ffe3c5f1d9c7a23c4dfe2034b96e9884ce00a1cf521e22393f9448c 0.600000000000 1793242 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": 1305651, "vin": [ { "gen": { "height": 1305641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35aec8631ffe3c5f1d9c7a23c4dfe2034b96e9884ce00a1cf521e22393f9448c" } } ], "extra": [ 1, 89, 221, 191, 135, 176, 92, 254, 51, 30, 64, 161, 140, 82, 219, 221, 213, 129, 227, 133, 61, 106, 233, 179, 143, 9, 145, 88, 17, 35, 85, 53, 203, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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