Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1294dc4e2c375229e79189e5e2a7e1c02f9e76be099fb0ca60c013a84f6455c9

Tx prefix hash: 59286a8dd79d5dcd5ff912ea9a3d19a48b63498f3e57cf462eab6aab82dcf28c
Tx public key: 2ccd81e8deba7fc949cac0f14423f71e712131e5ce9f972227f4e8fcc90c227c
Timestamp: 1579666355 Timestamp [UCT]: 2020-01-22 04:12:35 Age [y:d:h:m:s]: 05:043:01:56:00
Block: 50457 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1181298 RingCT/type: yes/0
Extra: 012ccd81e8deba7fc949cac0f14423f71e712131e5ce9f972227f4e8fcc90c227c02110000001ebd0f9f9f000000000000000000

1 output(s) for total of 417.653231118000 dcy

stealth address amount amount idx
00: c0d0c3f4912497a5a0a5110037a95651565a536f9f4fea26b376e46985805fd4 417.653231118000 93574 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": 50467, "vin": [ { "gen": { "height": 50457 } } ], "vout": [ { "amount": 417653231118, "target": { "key": "c0d0c3f4912497a5a0a5110037a95651565a536f9f4fea26b376e46985805fd4" } } ], "extra": [ 1, 44, 205, 129, 232, 222, 186, 127, 201, 73, 202, 192, 241, 68, 35, 247, 30, 113, 33, 49, 229, 206, 159, 151, 34, 39, 244, 232, 252, 201, 12, 34, 124, 2, 17, 0, 0, 0, 30, 189, 15, 159, 159, 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