Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e46af7cc08c5c64db86d75a51a5187404f82a18eb0ba4573507cb703461116f

Tx prefix hash: 6aa0c1f3a6bd2e6c706d853b311b7ed5586246604573a77d650e34e56d8d93c6
Tx public key: 6ec3c2edb7a4cceaf9accf3565b39afcab1a2b70082dc4f4f136966331b04ef0
Timestamp: 1706799277 Timestamp [UCT]: 2024-02-01 14:54:37 Age [y:d:h:m:s]: 00:344:05:54:35
Block: 948096 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246464 RingCT/type: yes/0
Extra: 016ec3c2edb7a4cceaf9accf3565b39afcab1a2b70082dc4f4f136966331b04ef00211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3d3ee71565640413e3f0980da21acd33530e3582a7698cb222e81720f80466c 0.600000000000 1406468 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": 948106, "vin": [ { "gen": { "height": 948096 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3d3ee71565640413e3f0980da21acd33530e3582a7698cb222e81720f80466c" } } ], "extra": [ 1, 110, 195, 194, 237, 183, 164, 204, 234, 249, 172, 207, 53, 101, 179, 154, 252, 171, 26, 43, 112, 8, 45, 196, 244, 241, 54, 150, 99, 49, 176, 78, 240, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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