Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfc1560cc0bc95d7cc0189f9d8bda28ed3be3fe1c796efd40392a5b085925349

Tx prefix hash: fc0a0e1c9c93c2a64464c343aa7a905ed26b06ac49e11a563f13643c21a56ab6
Tx public key: 49c1b444baa7a30058c20071e90d839011a56e60f6fbbc40b60eea2afca67a5d
Timestamp: 1669687669 Timestamp [UCT]: 2022-11-29 02:07:49 Age [y:d:h:m:s]: 02:136:06:18:47
Block: 641340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 619104 RingCT/type: yes/0
Extra: 0149c1b444baa7a30058c20071e90d839011a56e60f6fbbc40b60eea2afca67a5d02110000000275e3f0e9000000000000000000

1 output(s) for total of 4.602293871000 dcy

stealth address amount amount idx
00: 09b4c2323c3c82b136c9d79e9dc27ae7653e5d0abef54c787d4cc9ee7a4fba8f 4.602293871000 1081135 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": 641350, "vin": [ { "gen": { "height": 641340 } } ], "vout": [ { "amount": 4602293871, "target": { "key": "09b4c2323c3c82b136c9d79e9dc27ae7653e5d0abef54c787d4cc9ee7a4fba8f" } } ], "extra": [ 1, 73, 193, 180, 68, 186, 167, 163, 0, 88, 194, 0, 113, 233, 13, 131, 144, 17, 165, 110, 96, 246, 251, 188, 64, 182, 14, 234, 42, 252, 166, 122, 93, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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