Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be5e796b9c84fc148b4bf7db688258764852b215b94a4f804544aa82d666367e

Tx prefix hash: 8d6aa41a619f64bc81d7da47b491dabec25c5e19864276f3d9fdfc035a9e7167
Tx public key: 12461a41f8d6f4f0b3d8596ee971c2e7f85e2f33ea31f254dcfe696aae877782
Timestamp: 1737031473 Timestamp [UCT]: 2025-01-16 12:44:33 Age [y:d:h:m:s]: 00:059:23:48:09
Block: 1198599 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42671 RingCT/type: yes/0
Extra: 0112461a41f8d6f4f0b3d8596ee971c2e7f85e2f33ea31f254dcfe696aae877782021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17df9732d1f871a40ae7ed2319f2e8189d4158725c414b972a6f1aa162e4db7c 0.600000000000 1685224 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": 1198609, "vin": [ { "gen": { "height": 1198599 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17df9732d1f871a40ae7ed2319f2e8189d4158725c414b972a6f1aa162e4db7c" } } ], "extra": [ 1, 18, 70, 26, 65, 248, 214, 244, 240, 179, 216, 89, 110, 233, 113, 194, 231, 248, 94, 47, 51, 234, 49, 242, 84, 220, 254, 105, 106, 174, 135, 119, 130, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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