Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf0a52f98d17fbda406fb1358cce449af4094ba35204e8c8696ee3279f2e86e3

Tx prefix hash: a4200ab689c42b2f63ca1751a197eab2ffc0c137a09cccaa5098593d9ff1146b
Tx public key: ae57772b50b6a3183a2abc08a2cc6705c6a7680aad1fef2b10a0764c35f1bcf6
Timestamp: 1698465648 Timestamp [UCT]: 2023-10-28 04:00:48 Age [y:d:h:m:s]: 01:165:09:34:53
Block: 879243 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379208 RingCT/type: yes/0
Extra: 01ae57772b50b6a3183a2abc08a2cc6705c6a7680aad1fef2b10a0764c35f1bcf602110000000533af99f4000000000000000000

1 output(s) for total of 0.749381493000 dcy

stealth address amount amount idx
00: 88f608f4103ada667e1ad69c35fe4590d9366d83e0e065d3065d2809ab822523 0.749381493000 1334749 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": 879253, "vin": [ { "gen": { "height": 879243 } } ], "vout": [ { "amount": 749381493, "target": { "key": "88f608f4103ada667e1ad69c35fe4590d9366d83e0e065d3065d2809ab822523" } } ], "extra": [ 1, 174, 87, 119, 43, 80, 182, 163, 24, 58, 42, 188, 8, 162, 204, 103, 5, 198, 167, 104, 10, 173, 31, 239, 43, 16, 160, 118, 76, 53, 241, 188, 246, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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