Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6d5994423d754229da0255e1233b4b8d54e740a5d06484cd241d884c1ca875a

Tx prefix hash: 7aface55ef56630d8adb660a28a720939999ad94730ef50ef4cd3b7bc0965fbd
Tx public key: b26703a402df92c6e165ca7059c4b7715f72f67edcf23040d1ea6332b16a07f4
Timestamp: 1643289889 Timestamp [UCT]: 2022-01-27 13:24:49 Age [y:d:h:m:s]: 03:277:23:23:26
Block: 426370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 975568 RingCT/type: yes/0
Extra: 01b26703a402df92c6e165ca7059c4b7715f72f67edcf23040d1ea6332b16a07f4021100000001c9993c7f000000000000000000

1 output(s) for total of 23.727911222000 dcy

stealth address amount amount idx
00: fec3ccba0a64f317f2800f7fedf73d86741ac982c3062c38cb64d9b722d7f3bc 23.727911222000 835187 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": 426380, "vin": [ { "gen": { "height": 426370 } } ], "vout": [ { "amount": 23727911222, "target": { "key": "fec3ccba0a64f317f2800f7fedf73d86741ac982c3062c38cb64d9b722d7f3bc" } } ], "extra": [ 1, 178, 103, 3, 164, 2, 223, 146, 198, 225, 101, 202, 112, 89, 196, 183, 113, 95, 114, 246, 126, 220, 242, 48, 64, 209, 234, 99, 50, 177, 106, 7, 244, 2, 17, 0, 0, 0, 1, 201, 153, 60, 127, 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