Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bb0c590293b85ee5cb5372f3d8283fd5e73f66f102777e79aa062cf0b1e79b8

Tx prefix hash: 0d15413ba174f52fb159010ef18a2ba7f0792e280829b33d36b980a1c010646b
Tx public key: 439cf0187ee363a57bef8d8f57eb4fa0aba8d4d230cab6ecf4c67897a69d741c
Timestamp: 1749722171 Timestamp [UCT]: 2025-06-12 09:56:11 Age [y:d:h:m:s]: 00:151:18:47:43
Block: 1303378 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106181 RingCT/type: yes/0
Extra: 01439cf0187ee363a57bef8d8f57eb4fa0aba8d4d230cab6ecf4c67897a69d741c021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6332d471494ca8e7a7dce867229529de0bbfe6bede3d16e1797a1e39214fcc1 0.600000000000 1790957 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": 1303388, "vin": [ { "gen": { "height": 1303378 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6332d471494ca8e7a7dce867229529de0bbfe6bede3d16e1797a1e39214fcc1" } } ], "extra": [ 1, 67, 156, 240, 24, 126, 227, 99, 165, 123, 239, 141, 143, 87, 235, 79, 160, 171, 168, 212, 210, 48, 202, 182, 236, 244, 198, 120, 151, 166, 157, 116, 28, 2, 17, 0, 0, 0, 4, 191, 81, 178, 162, 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