Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b037fc87b8f11e686fadbf3f39419e30710a3344cfce401a13ead3150f9cc768

Tx prefix hash: e025e3743d2192c78581245f122dd6c4d872300c8c33205f1517f1367373be03
Tx public key: 37e9d6cae8b5079f3f0f3a87c8a8362dc4e3ec155196591935756c54f23cf8ae
Timestamp: 1749879801 Timestamp [UCT]: 2025-06-14 05:43:21 Age [y:d:h:m:s]: 00:232:06:36:35
Block: 1304636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163681 RingCT/type: yes/0
Extra: 0137e9d6cae8b5079f3f0f3a87c8a8362dc4e3ec155196591935756c54f23cf8ae02110000000301491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fdd3b95896d4abc2df4f2f18e86f8f95700a38dbd4c09a89071b685e89dabb31 0.600000000000 1792227 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": 1304646, "vin": [ { "gen": { "height": 1304636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fdd3b95896d4abc2df4f2f18e86f8f95700a38dbd4c09a89071b685e89dabb31" } } ], "extra": [ 1, 55, 233, 214, 202, 232, 181, 7, 159, 63, 15, 58, 135, 200, 168, 54, 45, 196, 227, 236, 21, 81, 150, 89, 25, 53, 117, 108, 84, 242, 60, 248, 174, 2, 17, 0, 0, 0, 3, 1, 73, 31, 136, 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