Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b12f3beadf1b60a5cd672da8c620bd743fdb0b1c179563acae71ba8368d32e1

Tx prefix hash: c0939196955e96c6ce9871cf85c5306c4f7035e32b40d525e86d4ec3277e3f0d
Tx public key: 561c2f32d8a0d408ed1a70a050f7726925451d234e204878a30eb6019b2ba573
Timestamp: 1668998993 Timestamp [UCT]: 2022-11-21 02:49:53 Age [y:d:h:m:s]: 02:173:22:11:18
Block: 635641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 646033 RingCT/type: yes/0
Extra: 01561c2f32d8a0d408ed1a70a050f7726925451d234e204878a30eb6019b2ba57302110000000271bd5189000000000000000000

1 output(s) for total of 4.806816103000 dcy

stealth address amount amount idx
00: 09a0922f14342d8cd0f5dd6d8fd4a4c92016ea41aa8beed453dd23ff188f3b22 4.806816103000 1074947 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": 635651, "vin": [ { "gen": { "height": 635641 } } ], "vout": [ { "amount": 4806816103, "target": { "key": "09a0922f14342d8cd0f5dd6d8fd4a4c92016ea41aa8beed453dd23ff188f3b22" } } ], "extra": [ 1, 86, 28, 47, 50, 216, 160, 212, 8, 237, 26, 112, 160, 80, 247, 114, 105, 37, 69, 29, 35, 78, 32, 72, 120, 163, 14, 182, 1, 155, 43, 165, 115, 2, 17, 0, 0, 0, 2, 113, 189, 81, 137, 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