Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d80a5a304ce75be90f5850fa4e6e27a74dd33675dadb26d0c9a4d1ea73ad2a5

Tx prefix hash: d44363b2bfa49637efeb55ad13e9fd467bafa583eba4211fceea01ce560c38fc
Tx public key: 919092b6ac90070a9961d7394110b097b5775c95e7a30ae991b2690aa3dbaa4b
Timestamp: 1703618181 Timestamp [UCT]: 2023-12-26 19:16:21 Age [y:d:h:m:s]: 01:329:04:52:29
Block: 921740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 494131 RingCT/type: yes/0
Extra: 01919092b6ac90070a9961d7394110b097b5775c95e7a30ae991b2690aa3dbaa4b021100000002ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13c6dd0f66943eae673d657413b37c2205d457c9b3630a0f531b22e696ea78d2 0.600000000000 1379434 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": 921750, "vin": [ { "gen": { "height": 921740 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13c6dd0f66943eae673d657413b37c2205d457c9b3630a0f531b22e696ea78d2" } } ], "extra": [ 1, 145, 144, 146, 182, 172, 144, 7, 10, 153, 97, 215, 57, 65, 16, 176, 151, 181, 119, 92, 149, 231, 163, 10, 233, 145, 178, 105, 10, 163, 219, 170, 75, 2, 17, 0, 0, 0, 2, 173, 86, 148, 172, 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