Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb1e1faa7f7036573d1e43d5309bb0f484c423e5603222e9fff8060124537fe1

Tx prefix hash: f476069a443989446a98f69c0cb384cf9d71ba2ad3f21e76e475cfb7f50ed053
Tx public key: 7bc4f2431173fb98f5df6b356be223c82777f9cef25b664afebd395b511f52f1
Timestamp: 1734116246 Timestamp [UCT]: 2024-12-13 18:57:26 Age [y:d:h:m:s]: 00:097:00:21:33
Block: 1174496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69123 RingCT/type: yes/0
Extra: 017bc4f2431173fb98f5df6b356be223c82777f9cef25b664afebd395b511f52f1021100000002e890f369000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49d938fea0b42955bf63f234f64fb4ee8b8d670358929194d1cae6f66837b0dc 0.600000000000 1660655 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": 1174506, "vin": [ { "gen": { "height": 1174496 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49d938fea0b42955bf63f234f64fb4ee8b8d670358929194d1cae6f66837b0dc" } } ], "extra": [ 1, 123, 196, 242, 67, 17, 115, 251, 152, 245, 223, 107, 53, 107, 226, 35, 200, 39, 119, 249, 206, 242, 91, 102, 74, 254, 189, 57, 91, 81, 31, 82, 241, 2, 17, 0, 0, 0, 2, 232, 144, 243, 105, 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