Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2436b1903e9f07ffaf9e412df4a043c8ec7364fbc2cc5a0fbe4e56d5c9b351a5

Tx prefix hash: 9e4f96ca0486b0c8971e7a917b2ef9d2a8e079f68daff3710ead181caa36d72d
Tx public key: 646c8cafe1d75bf16cb3a81ccd58883b4de2bf21f025760d2ae017a97fe29c4a
Timestamp: 1672800056 Timestamp [UCT]: 2023-01-04 02:40:56 Age [y:d:h:m:s]: 02:142:04:26:32
Block: 667113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 623349 RingCT/type: yes/0
Extra: 01646c8cafe1d75bf16cb3a81ccd58883b4de2bf21f025760d2ae017a97fe29c4a02110000000933af99f4000000000000000000

1 output(s) for total of 3.780747387000 dcy

stealth address amount amount idx
00: a26ca66f59bd49fcaae610ef7cf4cdc55e57b44a62ab0980893abafcda76c4e6 3.780747387000 1108278 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": 667123, "vin": [ { "gen": { "height": 667113 } } ], "vout": [ { "amount": 3780747387, "target": { "key": "a26ca66f59bd49fcaae610ef7cf4cdc55e57b44a62ab0980893abafcda76c4e6" } } ], "extra": [ 1, 100, 108, 140, 175, 225, 215, 91, 241, 108, 179, 168, 28, 205, 88, 136, 59, 77, 226, 191, 33, 240, 37, 118, 13, 42, 224, 23, 169, 127, 226, 156, 74, 2, 17, 0, 0, 0, 9, 51, 175, 153, 244, 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