Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27e5fb0d415db70238a240330e02d507ccb16ea125b6f0bf453bd225110b4c2d

Tx prefix hash: 3b481386fa506ec2aa416ae87471de1c2ad6d639f8e960a66a348272bb784ff6
Tx public key: f97433ce7baf7653276b039e43c3f1a9f2da83dfc7287c9cd8d711bbc71e8ac2
Timestamp: 1724585837 Timestamp [UCT]: 2024-08-25 11:37:17 Age [y:d:h:m:s]: 00:246:11:44:09
Block: 1095574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176051 RingCT/type: yes/0
Extra: 01f97433ce7baf7653276b039e43c3f1a9f2da83dfc7287c9cd8d711bbc71e8ac2021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3fcfca5bbabe21e4d716c449f306a7c47db24d81a366653f5cc814c1d5e4209a 0.600000000000 1570755 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": 1095584, "vin": [ { "gen": { "height": 1095574 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3fcfca5bbabe21e4d716c449f306a7c47db24d81a366653f5cc814c1d5e4209a" } } ], "extra": [ 1, 249, 116, 51, 206, 123, 175, 118, 83, 39, 107, 3, 158, 67, 195, 241, 169, 242, 218, 131, 223, 199, 40, 124, 156, 216, 215, 17, 187, 199, 30, 138, 194, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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