Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1780b510601831250f79ea1ee7f380ea39e5f11bf5dad26b23130a1b9bc1a79

Tx prefix hash: 9e554e73e55e034ad8f8e9cac77adc374cfde895159a50df1ad3af55ecc42d0a
Tx public key: b06b2e1738bca4dc1da8ffc64eb3594d781592d10804a39ecfc4a848bc8100b8
Timestamp: 1744326325 Timestamp [UCT]: 2025-04-10 23:05:25 Age [y:d:h:m:s]: 00:254:12:45:54
Block: 1258727 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179691 RingCT/type: yes/0
Extra: 01b06b2e1738bca4dc1da8ffc64eb3594d781592d10804a39ecfc4a848bc8100b8021100000007dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a09f258e9afbc07e7c46c97b7229946d7a02ea630cc264732b6c956193c451c9 0.600000000000 1745864 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": 1258737, "vin": [ { "gen": { "height": 1258727 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a09f258e9afbc07e7c46c97b7229946d7a02ea630cc264732b6c956193c451c9" } } ], "extra": [ 1, 176, 107, 46, 23, 56, 188, 164, 220, 29, 168, 255, 198, 78, 179, 89, 77, 120, 21, 146, 209, 8, 4, 163, 158, 207, 196, 168, 72, 188, 129, 0, 184, 2, 17, 0, 0, 0, 7, 219, 181, 113, 193, 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