Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3829753661f28bd449f772bda102ecbd190373dfa1a8b42f70aa23b6e106fa7b

Tx prefix hash: 3ee75e0bbd61f04917cfa1a8d4d6b27f7f3133de37e7f01cba5bbe7b17e8b4b0
Tx public key: 4e51de6ef778c29ac3785f95e72afcf06190a0a51f9c1d83197984f4ec62e1f9
Timestamp: 1722552811 Timestamp [UCT]: 2024-08-01 22:53:31 Age [y:d:h:m:s]: 00:159:01:14:03
Block: 1078710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113796 RingCT/type: yes/0
Extra: 014e51de6ef778c29ac3785f95e72afcf06190a0a51f9c1d83197984f4ec62e1f9021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cc9e3262c1582d0e540e27869b001338e228f17f40341714d5e10583df401d9 0.600000000000 1551357 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": 1078720, "vin": [ { "gen": { "height": 1078710 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cc9e3262c1582d0e540e27869b001338e228f17f40341714d5e10583df401d9" } } ], "extra": [ 1, 78, 81, 222, 110, 247, 120, 194, 154, 195, 120, 95, 149, 231, 42, 252, 240, 97, 144, 160, 165, 31, 156, 29, 131, 25, 121, 132, 244, 236, 98, 225, 249, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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