Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 597e9fbbf9315bad76aa08fd00553c2baa82ec5677c5aa872cddf5eeb18b9f2d

Tx prefix hash: 4679d91b9fc72517378a3d3e50b375a63d6a2be24b631cbebb3dc90b80a7fbfc
Tx public key: 3ded643ba193c73cc0efd733f4055196bd8fbbb7a8886931d2a92a9b3f3f4c8d
Timestamp: 1737833524 Timestamp [UCT]: 2025-01-25 19:32:04 Age [y:d:h:m:s]: 00:142:19:34:19
Block: 1205215 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101819 RingCT/type: yes/0
Extra: 013ded643ba193c73cc0efd733f4055196bd8fbbb7a8886931d2a92a9b3f3f4c8d021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0ed6cf3c41a6f063e816ba44a4cda967efe06848754253c2f08b2d8f03c4059 0.600000000000 1691912 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": 1205225, "vin": [ { "gen": { "height": 1205215 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0ed6cf3c41a6f063e816ba44a4cda967efe06848754253c2f08b2d8f03c4059" } } ], "extra": [ 1, 61, 237, 100, 59, 161, 147, 199, 60, 192, 239, 215, 51, 244, 5, 81, 150, 189, 143, 187, 183, 168, 136, 105, 49, 210, 169, 42, 155, 63, 63, 76, 141, 2, 17, 0, 0, 0, 8, 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