Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e588fe7af88d8f710b9ade6885158e653b08c66367d7a3f0e739ba5308039b92

Tx prefix hash: 7a4ee8c60f2505434bf11e01a1924235a5601bb83ce2e1d8fc54bbc71f94ea65
Tx public key: 23a89a1b5167d7e6f0db3a523a9f2c76b86de80d132874881ec3941f138791d5
Timestamp: 1684875303 Timestamp [UCT]: 2023-05-23 20:55:03 Age [y:d:h:m:s]: 01:234:07:18:29
Block: 766603 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 428887 RingCT/type: yes/0
Extra: 0123a89a1b5167d7e6f0db3a523a9f2c76b86de80d132874881ec3941f138791d502110000000475e3f0e9000000000000000000

1 output(s) for total of 1.769808220000 dcy

stealth address amount amount idx
00: fa36604941709f13f2e2393626d28586ee7843ba0d15c73e2044ca82688125ba 1.769808220000 1215652 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": 766613, "vin": [ { "gen": { "height": 766603 } } ], "vout": [ { "amount": 1769808220, "target": { "key": "fa36604941709f13f2e2393626d28586ee7843ba0d15c73e2044ca82688125ba" } } ], "extra": [ 1, 35, 168, 154, 27, 81, 103, 215, 230, 240, 219, 58, 82, 58, 159, 44, 118, 184, 109, 232, 13, 19, 40, 116, 136, 30, 195, 148, 31, 19, 135, 145, 213, 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