Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b3dd242a085550e4aee87fc555ec3533f5409c2ad8195d745f05e0e77292af0

Tx prefix hash: 7f7ef45d1fa9f814adf0015d0d6438817090108cf52134b352b938f8f64fee77
Tx public key: 0949ab624befe1b0d04f2e891ca6a08131d27662d275333a7fb40c6ecdd849a9
Timestamp: 1648546830 Timestamp [UCT]: 2022-03-29 09:40:30 Age [y:d:h:m:s]: 02:272:19:33:19
Block: 468828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 714550 RingCT/type: yes/0
Extra: 010949ab624befe1b0d04f2e891ca6a08131d27662d275333a7fb40c6ecdd849a9021100000002a8c141c5000000000000000000

1 output(s) for total of 17.162417691000 dcy

stealth address amount amount idx
00: bce6e7cb3a9e7c491e20f1d8c46e7c13c33874ad6a692932d2ec8af5c8a8ad3b 17.162417691000 887624 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": 468838, "vin": [ { "gen": { "height": 468828 } } ], "vout": [ { "amount": 17162417691, "target": { "key": "bce6e7cb3a9e7c491e20f1d8c46e7c13c33874ad6a692932d2ec8af5c8a8ad3b" } } ], "extra": [ 1, 9, 73, 171, 98, 75, 239, 225, 176, 208, 79, 46, 137, 28, 166, 160, 129, 49, 210, 118, 98, 210, 117, 51, 58, 127, 180, 12, 110, 205, 216, 73, 169, 2, 17, 0, 0, 0, 2, 168, 193, 65, 197, 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