Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb92a97a24d0f3279bafda7f2324fef8fb1a8f642e47256774e055407f883aa0

Tx prefix hash: 9bf245ce51632dbbd47b805119d585d494377ce55667e223690711b5325f1eae
Tx public key: a7c5e3c90e254df493ef6d0a1a86d6f7a64ecf76abe597a3f0bf207b449dfb6f
Timestamp: 1699516120 Timestamp [UCT]: 2023-11-09 07:48:40 Age [y:d:h:m:s]: 01:090:00:24:53
Block: 887744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325483 RingCT/type: yes/0
Extra: 01a7c5e3c90e254df493ef6d0a1a86d6f7a64ecf76abe597a3f0bf207b449dfb6f021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.702320927000 dcy

stealth address amount amount idx
00: 4840a39f26ff6050d787c7095a8bdc0b525cf926975f3f7d3acd19ff69b9e2d5 0.702320927000 1343639 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": 887754, "vin": [ { "gen": { "height": 887744 } } ], "vout": [ { "amount": 702320927, "target": { "key": "4840a39f26ff6050d787c7095a8bdc0b525cf926975f3f7d3acd19ff69b9e2d5" } } ], "extra": [ 1, 167, 197, 227, 201, 14, 37, 77, 244, 147, 239, 109, 10, 26, 134, 214, 247, 166, 78, 207, 118, 171, 229, 151, 163, 240, 191, 32, 123, 68, 157, 251, 111, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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