Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8048d875a667388098dc2d2549703dbb071b06dbe384e015b5025dbe11b7dd45

Tx prefix hash: 5f5ce694ff3880f3b6009908c28ee53ffb15ed620466c2cc724f7b14e5277ee3
Tx public key: 7812e1104b18b594f2a5ab9430b8c4791635673819d3ff1547ad1279c6e2991c
Timestamp: 1705172324 Timestamp [UCT]: 2024-01-13 18:58:44 Age [y:d:h:m:s]: 01:078:03:02:02
Block: 934608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316943 RingCT/type: yes/0
Extra: 017812e1104b18b594f2a5ab9430b8c4791635673819d3ff1547ad1279c6e2991c0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3b8b3a2c01514acdf2c7f564365b450dba3e7543ceff0f8d8c7da7eea99ae9a 0.600000000000 1392622 of 15

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": 934618, "vin": [ { "gen": { "height": 934608 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3b8b3a2c01514acdf2c7f564365b450dba3e7543ceff0f8d8c7da7eea99ae9a" } } ], "extra": [ 1, 120, 18, 225, 16, 75, 24, 181, 148, 242, 165, 171, 148, 48, 184, 196, 121, 22, 53, 103, 56, 25, 211, 255, 21, 71, 173, 18, 121, 198, 226, 153, 28, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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