Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50fabbc05c181481950de8d7f24662aa9bad654388a6f4f34ca2904caedd0d2b

Tx prefix hash: ae4e1e00c741435514ac995df4ca6da90a8cd2c8e0d295f7ab7183675d4f9b8e
Tx public key: 3294f20a110f2477bf26aa9775094e1c2bea18f9c5a5e67882cf49553e0501ab
Timestamp: 1722380726 Timestamp [UCT]: 2024-07-30 23:05:26 Age [y:d:h:m:s]: 00:250:05:37:11
Block: 1077287 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178737 RingCT/type: yes/0
Extra: 013294f20a110f2477bf26aa9775094e1c2bea18f9c5a5e67882cf49553e0501ab021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef2d4af7d1fac12b81a5c970c9dee3f38ecf8e054ff4b072f2356068c9726933 0.600000000000 1549834 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": 1077297, "vin": [ { "gen": { "height": 1077287 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef2d4af7d1fac12b81a5c970c9dee3f38ecf8e054ff4b072f2356068c9726933" } } ], "extra": [ 1, 50, 148, 242, 10, 17, 15, 36, 119, 191, 38, 170, 151, 117, 9, 78, 28, 43, 234, 24, 249, 197, 165, 230, 120, 130, 207, 73, 85, 62, 5, 1, 171, 2, 17, 0, 0, 0, 2, 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