Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62119a570884f6b6b9de16ac3793e2a275e3178e03ca4cfa6569d94070d9f2da

Tx prefix hash: b0d2e083a35569b254b467aaecb749a0c8fff96a06f6056793b05fcb023d001e
Tx public key: 2ff3ce1ce4d51add7a3c39dde57d5b977eff89760465cc0fafb4ffd09a274882
Timestamp: 1703735330 Timestamp [UCT]: 2023-12-28 03:48:50 Age [y:d:h:m:s]: 01:317:01:50:45
Block: 922708 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485452 RingCT/type: yes/0
Extra: 012ff3ce1ce4d51add7a3c39dde57d5b977eff89760465cc0fafb4ffd09a27488202110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b79b7b5980d22eba89d5d7bd514b1a84fb5ded3a2b95941c04165c0224a61c53 0.600000000000 1380412 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": 922718, "vin": [ { "gen": { "height": 922708 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b79b7b5980d22eba89d5d7bd514b1a84fb5ded3a2b95941c04165c0224a61c53" } } ], "extra": [ 1, 47, 243, 206, 28, 228, 213, 26, 221, 122, 60, 57, 221, 229, 125, 91, 151, 126, 255, 137, 118, 4, 101, 204, 15, 175, 180, 255, 208, 154, 39, 72, 130, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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