Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec18bfba71d286a9009935625f1ea3170c2cfedb02617ea54be445dddccb9475

Tx prefix hash: 4772c27f8cf63c47108a955377de5dd1f2eecbefa0acbfc177dd55088708084e
Tx public key: 5de74f3a7c5b04d88f85727069781faa7f7c73261181bcbdb609da792299c30b
Timestamp: 1696674683 Timestamp [UCT]: 2023-10-07 10:31:23 Age [y:d:h:m:s]: 01:259:16:05:23
Block: 864374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 446469 RingCT/type: yes/0
Extra: 015de74f3a7c5b04d88f85727069781faa7f7c73261181bcbdb609da792299c30b02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.839402300000 dcy

stealth address amount amount idx
00: 04d3c44cdc8ccbfa06fc1a07d7b29b7e49bdf283958b69111d94ea61c2dc943a 0.839402300000 1318886 of 0

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": 864384, "vin": [ { "gen": { "height": 864374 } } ], "vout": [ { "amount": 839402300, "target": { "key": "04d3c44cdc8ccbfa06fc1a07d7b29b7e49bdf283958b69111d94ea61c2dc943a" } } ], "extra": [ 1, 93, 231, 79, 58, 124, 91, 4, 216, 143, 133, 114, 112, 105, 120, 31, 170, 127, 124, 115, 38, 17, 129, 188, 189, 182, 9, 218, 121, 34, 153, 195, 11, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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