Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94eeb70bef9c0f314069f48fe1b6eed5f95b63f1e8e41456c7d049bc66a51363

Tx prefix hash: 935637c80d73701b5086d4f3610e0cc18a2239002694c5e93dc2cbfcb1a0d867
Tx public key: 9284b7132518582d2f8260aab1e9f2908cd314514bd81febae59604b87fb38fc
Timestamp: 1729424956 Timestamp [UCT]: 2024-10-20 11:49:16 Age [y:d:h:m:s]: 00:191:22:26:53
Block: 1135682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137001 RingCT/type: yes/0
Extra: 019284b7132518582d2f8260aab1e9f2908cd314514bd81febae59604b87fb38fc02110000000aa6b5e9fb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03f1f16596ae50a2b5ce82c7e5db4a9309b34d1e9fc5a7024bb46ec87bb125b5 0.600000000000 1619021 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": 1135692, "vin": [ { "gen": { "height": 1135682 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03f1f16596ae50a2b5ce82c7e5db4a9309b34d1e9fc5a7024bb46ec87bb125b5" } } ], "extra": [ 1, 146, 132, 183, 19, 37, 24, 88, 45, 47, 130, 96, 170, 177, 233, 242, 144, 140, 211, 20, 81, 75, 216, 31, 235, 174, 89, 96, 75, 135, 251, 56, 252, 2, 17, 0, 0, 0, 10, 166, 181, 233, 251, 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