Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3685edadf07a0723f072e0f1996eb8d2c3ca2018fe92db412d424b9a8bcdfe89

Tx prefix hash: 230f9af1a2736ce2e2ddecb5b95d840e2860a08f9a7f1dc0f913c0c65d1447e7
Tx public key: 5f54dd6a85c836dd09d17272f3d29049b5632170c439be74df7370e2b3f942a5
Timestamp: 1745729011 Timestamp [UCT]: 2025-04-27 04:43:31 Age [y:d:h:m:s]: 00:208:14:21:27
Block: 1270348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146799 RingCT/type: yes/0
Extra: 015f54dd6a85c836dd09d17272f3d29049b5632170c439be74df7370e2b3f942a50211000000042609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ead0db70a9fa9d8096126e83ddae6bd96fbb517c68973bb08227f10b4bc5d9f8 0.600000000000 1757591 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": 1270358, "vin": [ { "gen": { "height": 1270348 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ead0db70a9fa9d8096126e83ddae6bd96fbb517c68973bb08227f10b4bc5d9f8" } } ], "extra": [ 1, 95, 84, 221, 106, 133, 200, 54, 221, 9, 209, 114, 114, 243, 210, 144, 73, 181, 99, 33, 112, 196, 57, 190, 116, 223, 115, 112, 226, 179, 249, 66, 165, 2, 17, 0, 0, 0, 4, 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