Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0e89055fd4130b7c755dd4584e0a0f61cfab77e5caa3ad054104463a67e110e

Tx prefix hash: 50c283dfb57d13165f8d3ac399d05a0b9c10a03526ae59dd657cb001efc5f123
Tx public key: a2b3613591f6cbcd98f1036f4d8583e7543713aee94332b6fc48b06f0794348c
Timestamp: 1645483574 Timestamp [UCT]: 2022-02-21 22:46:14 Age [y:d:h:m:s]: 02:282:17:34:24
Block: 443639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 721465 RingCT/type: yes/0
Extra: 01a2b3613591f6cbcd98f1036f4d8583e7543713aee94332b6fc48b06f0794348c0211000000052e6b1fd5000000000000000000

1 output(s) for total of 20.798888071000 dcy

stealth address amount amount idx
00: c0de34e5ab47c1ba7c27c35061c8e732236f00bd018b79f55ad45036a0280db4 20.798888071000 856728 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": 443649, "vin": [ { "gen": { "height": 443639 } } ], "vout": [ { "amount": 20798888071, "target": { "key": "c0de34e5ab47c1ba7c27c35061c8e732236f00bd018b79f55ad45036a0280db4" } } ], "extra": [ 1, 162, 179, 97, 53, 145, 246, 203, 205, 152, 241, 3, 111, 77, 133, 131, 231, 84, 55, 19, 174, 233, 67, 50, 182, 252, 72, 176, 111, 7, 148, 52, 140, 2, 17, 0, 0, 0, 5, 46, 107, 31, 213, 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