Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da9d6dfae744c9761011613f6bcf1666a157d5bb4f3df15c229d4551e36b18f7

Tx prefix hash: 74508574f9917976d9c9378b8fb42a41fb0e739a7e802c01e204717c2f358b5e
Tx public key: 09e002dbf3ba39d8950372a7f357a8f5f1e78d7e3ac910fa1eb1bac85621992d
Timestamp: 1709493238 Timestamp [UCT]: 2024-03-03 19:13:58 Age [y:d:h:m:s]: 00:331:07:27:46
Block: 970454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236895 RingCT/type: yes/0
Extra: 0109e002dbf3ba39d8950372a7f357a8f5f1e78d7e3ac910fa1eb1bac85621992d02110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f099918528630208973874b1561d246fd8014d2f02626ebfb91f119af321809b 0.600000000000 1430307 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": 970464, "vin": [ { "gen": { "height": 970454 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f099918528630208973874b1561d246fd8014d2f02626ebfb91f119af321809b" } } ], "extra": [ 1, 9, 224, 2, 219, 243, 186, 57, 216, 149, 3, 114, 167, 243, 87, 168, 245, 241, 231, 141, 126, 58, 201, 16, 250, 30, 177, 186, 200, 86, 33, 153, 45, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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